CompilerNotes ============= if you change ANYTHING in the Structures.h file you MUST rebuild **ALL** the source code, starting with the libraries... If you modify the GUI's using designer make sure that you change all occurences of NGad[ to NewGad[ in the .C and the .H file it produces, as well as changing the FreeImages; to FreeImages(); at the bottom of the .C file it produces.. To compile stuff, first double click !Nuke_Objects! then click BUILD, then if build works click UPDATE to copy the output to the right place.. !Nuke_Objects! and UPDATE are scripts.. (plain ASCII) Problems So Far: ================ * Can't have door options more than 80 charaters when using the door tester.. - Irellevent, door tester is not used anymore.. * Locking/Sharing of USER.DATA needs to be updated so that when user.data is opened by any routine the routine should keep retrying until it can access it. * also, when writing to user.data there should be a access_write lock on it from the routine that is doing the write operation.. * If you are using CPR (comes with SAS/C) then be aware that it patches OpenDevice() but doesn't do it quite right, as sometimes when you open or close a device, cpr causes the program doing the open/close to software fail. I found this out after much hair loss i can tell you!!! * crash if opendevice fails (try USRserial.device instead of USRSerial.device) * if you have a watch window open it WILL slow down the output of ansi on te users terminal program. (but this happens on ALL bbs systems, not just HBBS!) Undocumented Stuff ================== There are lots of things that are either in the config files but not in the .guides and vice version, but most of them you can work out, here are a few that need a bit of explanation... _Debug=YES|NO in "Commands/System" files. When this is enabled HBBS will not automatically execute your door, instead you must start it yourself, you will be told what options to pass to it and these MUST be exactly the same as what is displayed. This option was put in so that door coders could run thier doors from debuggers very easily! (Unlike /X :-) you can use codeprobe on doors by enabling debug for the door and then enter in the cli "CPR " Known Bugs ========== Lack of user.data file stalls system, use the script "MakeData" to restore a blank user.data file! need to replace all \033[0m's sent to the console.device with \033[0;37m as there is a bug in the console device which causes all the text after an ansi reset to be RED instead of WHITE. // Hence the /X problem that made all white ansi be red, until i patch the console.device (probably not for a while as i have NO idea how to do it...) door coders should send [0;37m to reset the console device instead of [0m. this way the problem will never show up. As I've not put in the checking for "required options" for all config files (E.G. NodeLocal and Device) you might get some odd results if you don't set ALL config options to something.. sometimes when you shutdown a node with a modem attached it does not retry the hangupstring..